home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
wildcat
/
badlist.zip
/
BADLIST.DOC
next >
Wrap
Text File
|
1992-02-09
|
4KB
|
112 lines
BADLIST.EXE (c) 1992 Karl Schneider
8505 Woodwick Ct.
Tampa, FL 33615
813-884-9661 voice DAYS/EVES
" " " BBS MIDNIGHT to 7:00 A.M.
EASTERN TIME ONLY. 14400 HST
Full access 1st call.
For WILDCAT! v3.x+ only!
BADLIST is a quick little program asked for by Tim Williams...it creates
a text file consisting of only the BASE filenames of all files in your
Wildcat Files database. It looks like this: (well, mine does...):
FILEPROB
WC3FLIST
OFFLINE
PCBZIP
UPDNWC30
DOORSEC
...and so on.
One possible (maybe the only) use for this utility is to add this
list to your BADFILES.LST so that someone cannot, for example, Download
SOMEFILE.ZIP, Unzip it, put it back into ARJ, LZH, ARC format, etc., and
attempt to upload SOMEFILE.ARJ for undeserved credit.
This can be run in an event, or at any time you wish, it is VERY FAST.
It can even be executed in a POSTCALL.BAT to keep completely up to date.
See the *** WARNING *** below!
File sharing is supported, so it's not necessary to shut down nodes.
You probably (and should) have other file names in BADFILES.LST, such
as CAT.BAT, ZUP.BAT, etc. (WC manual P. 142 covers this), so you should
do something like this to keep those names, and add those produced by
this program:
Use BADLIST either after each call (in POSTCALL.BAT) or in an EVENT.
Either way, this is what to do:
1. Copy your original BADFILES.LST to BADFILES.SAV or something similar.
2. To run this program, add something like this to the commands in
the corresponding Batch file:
cd\wc30
copy badfiles.sav badfiles.lst
badlist>>badfiles.lst
^^
|__don't forget the '>>' !
This will cause the listing to be ADDED to BADFILES.LST when it is
executed, and your original entries will be preserved.
Change the 'cd\wc30' to correspond to your WILDCAT setup.
3. You can place BADLIST.EXE anywhere in your PATH, but it must be
executed from your Wildcat Home directory.
-------------------------------------------------------------------------
************ WARNING *************
Using this program can prevent the 'allow overwriting by original up-
loader' option in MAKEWILD from working! Here is how I handle this
small problem:
Update the BADFILES.LST after EACH CALL in POSTCALL.BAT using the method
above.
Set up a DOOR or HOOK of your choice that does just the following:
DEL \WC30\BADFILES.LST
COPY \WC30\BADFILES.SAV \WC30\BADFILES.LST
(Change the pathnames as needed to fit your system.)
This restores your 'original' badfiles.lst, containing the programs
you do not want ANYONE uploading, EVER, but will allow the ORIGINAL
uploader (IF HIS SECURITY LEVEL IS AUTHORIZED TO DO SO) to over-write.
Set the MENU Minimum Security for this Door or Hook to whatever you
have set in MAKEWILD to allow over-writing. If you have an odd sec-
urity arrangement where some LOWER security levels are allowed to
over-write and some HIGHER ones are NOT, you will need to grab my
DOORSEC.ZIP utility which will restrict access to a Door or Hook to
a specified EXACT sec level.
I edited my BADFILES.BBS to say something like:
@FIRST@, the file you are attempting to upload is either RESERVED
or ALREADY EXISTS on this system. If you are authorized to OVER-WRITE
your uploads, you may press Z from the Files Menu to clear the flag!
Thanks. Karl
As you can see, this doesn't actually 'clear a flag'...it merely erases
the previously created BADFILES.LST and replaces it with the filenames
you _for sure_ don't want uploaded!
I have tested this on my own system with no problems. If you find a
use for this program, I request a nominal registration of $5 or more
to the above address. Any contribution of $30 or more will give you
full support on ALL my Wildcat 3.x+ utility programs, and if you're
already a 'registered' user, you may use this program with no further
obligation. As usual, there are no warranties, expressed or implied,
as to the usability or safety of this software. I don't believe there
is any way it can cause a problem, but if it does, I'm not responsible.
(At least, not legally...! <g>)
Thanks, Karl Schneider
-eof-